|
In project management, a death march is a project where the members feel it is destined to fail, or requires a stretch of unsustainable overwork. The general feel of the project reflects that of an actual death march because the members of the project are forced to continue the project by their superiors against their better judgment. The fields whose project management practice first named these related phenomena are software development and software engineering. Other fields have since recognized the same occurrence in their own spheres and have adopted the name. Death marches of the destined-to-fail type usually are a result of unrealistic or overly optimistic expectations in scheduling, feature scope, or both, and often include lack of appropriate documentation or relevant training and outside expertise that would be needed to do the task successfully. The knowledge of the doomed nature of the project weighs heavily on the psyche of its participants, as if they are helplessly watching themselves and their coworkers being forced to torture themselves and march toward death. Often, the death march will involve desperate attempts to right the course of the project by asking team members to work especially grueling hours (14-hour days, 7-day weeks, etc.) or by attempting to "throw (enough) bodies at the problem", often causing burnout. Often, the discomfort is heightened by the knowledge that "it didn't have to be this way," that is, that if the company wanted to achieve the goal of the project, it could have done so in a successful way if it had been managed competently (such as by devoting the obviously required resources, including bringing all relevant expertise, technology, or applied science to the task rather than just whatever incomplete knowledge a few employees happened to know already). Patent underresourcing is especially offensive at a large corporation with sufficiently deep pockets; at least at small companies, a gap between resources and needs is understandable, but at large, profitable, cash-rich companies, underresourcing is not a necessity and thus feels to most workers like stupidity. Business culture pressures, such as the long-noted phenomenon of corporations pursuing short-term maximization of profits via cost cutting or avoidance that is damaging to long-term best interest, may play a role in addition to mere incompetence. Among the most infamous death march projects are the Denver Airport baggage handling system and WARSIM, a U.S. Army wargame.〔(【引用サイトリンク】 title=WARSIM )〕〔(【引用サイトリンク】 url = http://web.archive.org/web/20101129022132/http://peostri.army.mil/PAO/publicinfo/FILES/WarSim.pdf )〕 The latter project was originally called WARSIM 2000 at its inception in the early 1990s. WARSIM was eventually used in the North Carolina National Guard's Brigade Warfighter Exercise in January 2013. The WARSIM schedule slipped many times. Moreover, WARSIM has a clumsy architecture that requires enough servers to fill a small room, while earlier "legacy" wargames run efficiently on a single standard desktop workstation. The term "death march" in this context was discussed at length in Edward Yourdon's book ''Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects'' (ISBN 0130146595), which has a second edition simply titled ''Death March'' (ISBN 013143635X). Yourdon's definition: "Quite simply, a death march project is one whose 'project parameters' exceed the norm by at least 50 percent." 〔(【引用サイトリンク】 title=What is a Death March Project and Why Do They Happen? )〕 ==See also== * Brooks's law * Escalation of commitment * Optimism bias * Planning fallacy * Wishful thinking 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Death march (project management)」の詳細全文を読む スポンサード リンク
|